Dynamically adjusting video merchandising to reflect user preferences

ABSTRACT

One embodiment of the present invention sets forth a technique for displaying scenes included in media assets. The technique includes selecting a first scene included in a first video asset based on one or more preferences and metadata associated with multiple scenes. The first video asset is one of multiple video assets, and each scene included in the multiple scenes is included in one of the video assets included in the multiple video assets. The technique further includes displaying the first scene within a first portion of a display area.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of co-pending U.S. patent applicationtitled, “DYNAMICALLY ADJUSTING VIDEO MERCHANDISING TO REFLECT USERPREFERENCES,” filed on Feb. 20, 2017 and having Ser. No. 15/437,378,which is a divisional of co-pending U.S. patent application titled,“DYNAMICALLY ADJUSTING VIDEO MERCHANDISING TO REFLECT USER PREFERENCES,”filed on Aug. 21, 2015 and having Ser. No. 14/832,988, which claims thepriority benefit of U.S. Provisional Application titled, “DYNAMICALLYADJUSTING VIDEO MERCHANDISING TO REFLECT USER PREFERENCES,” filed onAug. 22, 2014 and having Ser. No. 62/040,993. The subject matter ofthese related applications is hereby incorporated herein by reference.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates generally to computer processing and, morespecifically, to dynamically adjusting video merchandising to reflectuser preferences.

Description of the Related Art

Attracting and maintaining customer interest in video assets using avariety of “merchandising” techniques is an important aspect of manyvideo asset distribution systems. Typically, as part of merchandisingvideo assets, a user interface included in the video asset distributionsystem is configured to present information to a user about a selectedvideo asset in an attempt to convince the user that he or she wouldenjoy the selected video asset. In general, video asset distributionsystems implement one or more different techniques for presenting suchinformation to users.

In one technique, the user interface included in the video assetdistribution system is configured to present text-based information tousers. For example, such a user interface could display a video assetselection menu that includes a variety of icons, where each iconrepresents a different video asset. Upon detecting user interest in aparticular icon, the video asset distribution system could display apop-up that includes text describing the video asset associated with theicon in favorable terms, such as excerpts from positive reviews,descriptions of interesting aspects of the video asset, etc.

In another technique, the user interface included in the videodistribution system is configured to present information to usersthrough still-images. In such an approach, upon detecting a userselection, such a video distribution system could present a series ofstill-images designed to arouse a particular user interest. For example,to market an action movie, the video asset distribution system couldsequentially present three still-images to the user—a still-image of thestar of the movie, a still-image of an explosion, and a still-image of aknife fight. In some implementations, both text-based information andstill-images can be displayed to users simultaneously.

One drawback to the above techniques is that presenting text-basedinformation and still-images to users is contextually inconsistent withthe general user experience associated with watching video assets.Imposing contextually inconsistent merchandising information on aparticular user can cause the user to quickly lose interest in the videoasset, resulting in the user choosing not to select and watch the videoasset. Further, when a user does select and watch a video asset, afterplayback of the video asset is complete, presenting the user withtext-based information and still-images could result in a loss ofmomentum. Consequently, the user may choose not to select and watchanother video asset.

As the foregoing illustrates, what is needed in the art are moreeffective techniques for marketing video assets to users through videoasset distribution systems.

SUMMARY OF THE INVENTION

One embodiment of the present invention sets forth a method fordisplaying scenes included in media assets. The method includesselecting a first scene included in a first video asset based on one ormore preferences and metadata associated with multiple scenes, where thefirst video asset is included in multiple video assets, and each sceneincluded in the multiple scenes is included in one of the video assetsincluded in the multiple video assets; and displaying the first scenewithin a first portion of a display area.

One advantage of disclosed techniques for displaying scenes is thatvideo asset engines may leverage these techniques to effectivelymerchandise video assets. More specifically, a video asset engine mayselect personalized scenes and present the selected scenes in acontextually-relevant manner. Consequently, the video asset engine isable to increase the likelihood of attracting and maintaining userinterest in the video assets compared to video distribution systems thatimplement conventional merchandising techniques based on user-agnosticstill-images and/or text.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the presentinvention can be understood in detail, a more particular description ofthe invention, briefly summarized above, may be had by reference toembodiments, some of which are illustrated in the appended drawings. Itis to be noted, however, that the appended drawings illustrate onlytypical embodiments of this invention and are therefore not to beconsidered limiting of its scope, for the invention may admit to otherequally effective embodiments.

FIG. 1 is a block diagram of a video asset distribution systemconfigured to implement one or more aspects of the invention;

FIG. 2 is a conceptual diagram illustrating a video dissector configuredto generate the per-scene classification metadata, according to variousembodiments of the present invention;

FIG. 3 is a conceptual diagram illustrating how the video asset enginedisplays, over time, a graphical user interface tailored to an actionfan, according to various embodiments of the present invention; and

FIG. 4 is a flow diagram of method steps for selecting and playing backuser-relevant scenes via a graphical user interface, according tovarious embodiments of the present invention;

FIG. 5 is a conceptual diagram illustrating how the video asset enginedisplays, over time, a tailored trailer to a user, according to variousembodiments of the present invention;

FIG. 6 is a flow diagram of method steps for displaying a tailoredtrailer to a user, according to various embodiments of the presentinvention.

FIG. 7A is a conceptual diagram illustrating how the video asset enginecontrols multiple logical decoders, according to various embodiments ofthe present invention;

FIG. 7B is a conceptual diagram illustrating how the video asset enginecompensates for a network buffer depth according to various embodimentsof the present invention; and

FIG. 8 is a flow diagram of method steps for displaying video assets viamultiple decoders, according to various embodiments of the presentinvention.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a more thorough understanding of the present invention. However,it will be apparent to one of skill in the art that the presentinvention may be practiced without one or more of these specificdetails.

Video Asset Distribution System

FIG. 1 is a block diagram of a video asset distribution system 100configured to implement one or more aspects of the invention. As shown,the video asset distribution system 100 includes a cloud 130 (e.g.,encapsulated shared resources, software, data, etc.) connected to avariety of consumer devices capable of displaying video assets. Suchconsumer devices include, without limitation, a computer 102, a laptop110, a smartphone 120, a smart television 122, a game console 124, atablet 128, television-connected devices (not shown), handheld devices(not shown), and streaming entertainment devices (not shown).

As used herein, a video asset refers to any item that includes videocontent. Video assets may also include additional content, such as audiocontent, and may be manipulated (e.g., stored, encoded, compressed,transmitted, etc.) using any mechanisms known in the art. For example,one video asset may be a movie that is stored as a compressedaudio-video file, transmitted via the internet, and then decompressedfor display purposes.

In some embodiments, the consumer device is capable of running aweb-browser configured to display a graphical user interface thatenables the user to interact with the video assets. The implementationof the graphical user interface may differ based on the consumer device.For example, the laptop 110 could be configured to present the graphicaluser interface via a web-browser to enable users to browse video assets,select video assets, download video assets, and/or playback videoassets.

The cloud 130 may include any number of compute instance 140 configuredwith any number (including zero) of central processing units (CPUs) 142,graphics processing units (GPUs) 144, memory 146, etc. The cloud 130delivers video services, including both video and audio streams,associated with the video assets to the consumer devices over a network,such as the Internet, via a video asset engine 160. The video assetengine 160 includes logic that manages one or more graphical userinterfaces. To generate viewer interest in video assets, the video assetengine 160 is configured to perform video merchandising, such as byadvertising video assets using scenes (e.g., any number of consecutiveframes) from the video assets as “teasers.”

Notably, the video asset engine 160 dynamically selects and displaysscenes based on user preferences 150 and previous user interactions. Theuser preferences 150 include specific metadata tags for which the userof the video asset engine 160 has explicitly or implicitly expressedinterest or disinterest. Explicit evidence may include a list ofmetadata tags for which the user has explicitly expressed a preference.In operation, explicit evidence may be gathered based on the userproviding explicit information regarding specific metadata tags. Forexample, the user may explicitly indicate that the “Comedy” metadata tagis of interest, while the “Horror” metadata tag is not of interest.Implicit evidence may include a list of metadata tags for which the userhas implicitly expressed a preference. In operation, implicit evidencemay be gathered based on the interactions of the user with digitalcontent associated with specific metadata tags. For example, the usermay assign a negative rating to digital content associated with the“Comedy” metadata tag, or the user may repeatedly request digitalcontent with the “Horror” metadata tag. In such a manner, a list ofmetadata tags for which the user has implicitly expressed interest ordisinterest is gathered. In some embodiments, only digital content theuser has interacted with in the recent past is used to determine thelist of metadata tags in which the user is implicitly interested ordisinterested. In other embodiments, implicit evidence and explicitevidence may be based on any type of user data. Such user data caninclude any information relevant to a user or relevant to identifyingthe user preferences 150, for example, and without limitation, age,gender, socio economic information, geographic information, etc.Further, the user data may be based on any number of explicit settingsand any type of historical viewing statistics.

In operation, the video asset engine 160 selects targeted scenes withinvideo assets based on the user preferences 150 and additional userinteractions. In general, the video asset engine 160 implements amatching algorithm designed to find similarities between the userpreferences 150 and per-scene classification metadata 170. For eachscene, the per-scene classification metadata 170 may include a varietyof data, such as a “Comedy” metadata type or an age classification, thatidentify characteristics of users that are expected to enjoy the scene.Further, the per-scene classification metadata 170 may include any typeof data, at any granularity, that may indicate the general and/oruser-specific appeal of a video asset and/or a specific scene includedin a video asset. For example, the per-scene classification metadata 170may include information regarding the actors featured in the videoasset, the actresses featured in the video asset, release data, qualityrating, motion picture rating, available display resolutions, activitylevel, popularity, tone, location, plot, length, and so forth. The videoasset engine 160 may implement any technically feasible algorithm tomatch the user preferences 160 and the per-scene classification metadata170.

FIG. 2 is a conceptual diagram illustrating a video dissector 220configured to generate the per-scene classification metadata 170,according to various embodiments of the present invention. The videodissector 220 processes a video asset 210 (e.g., a movie), decomposesthe video asset 210 into multiple scenes, and then generates theper-scene classification metadata 170.

As shown, the video dissector 220 includes, without limitation, a scenesegment detector 222, a scene analyzer 224, and a scene classifier 226.The scene segment detector 222 partitions the video asset 210 intodistinct scenes, each scene consisting of multiple contiguous frames.Subsequently, the scene analyzer 224 examines each scene to determinescene-specific characteristics that imply classifications. For example,the scene analyzer 224 may determine that a scene includes multipleguns. Next, the scene classifier 226 uses the characteristics to derivegeneral classifications. For example, the scene classifier 226 maydetermine that an abundance of guns in a scene implies a relatively highlevel of violence.

Advantageously, the video asset engine 130 may implement the per-sceneclassification metadata 170 in conjunction with the user preferences 150to fine-tune video merchandising at the scene-level granularity,increasing the likelihood of appealing to user interest.

Capturing User Interest

FIG. 3 is a conceptual diagram illustrating how the video asset engine160 displays, over time, a graphical user interface (GUI) tailored to anaction fan, according to various embodiments of the present invention.As shown, a sequence of four snapshots depicts an action fan viewingexperience as time passes in a GUI window, labelled as display 310.

In the first time-snapshot, the video asset engine 160 displays a movieselection menu within a lower portion of the display 310 and receives anaction fan selection 325 of action movie “E.” In response, because theuser preferences 150 indicate that the user is an action fan, the videoasset engine 160 selects a targeted action scene from action movie E 320based on the per-scene classification metadata 170 associated with thevarious scenes from action movie “E.” In general, the video asset engine160 may implement any number of technically feasible heuristics toselect a scene that is likely to appeal to a user's interests (e.g., aninterest in action movies). For example, if the user preferences 150indicate that the action fan has a preference for martial arts scenes,then the video asset engine 160 could select an extended martial artssequence as the targeted action scene from action movie E 320. The videoasset engine 160 then displays the targeted action scene from actionmovie E 320 within an upper portion of the display 310, allowing theaction fan to “preview” action movie E while continuing to peruse themovie selection menu displayed in the lower portion of the display 310.

In some embodiments, the video asset engine 160 may detect a loss ofinterest in a particular scene and select a different scene to displayto a user in order to maintain the interest of the user. For example,after a relatively short time compared to the length of the targetedaction scene from action movie E 320, the video asset engine 160 detectsa loss of interest in action movie E 335. More specifically, as shown inthe second time-snapshot, the video asset engine 160 detects an actionfan selection 345 of comedy movie “B.”

In the second time-snapshot, the video asset engine 160 responds to theaction fan selection 345 of comedy movie “B.” Notably, because the userpreferences 150 indicate that the user is an action fan, the video assetengine 160 selects a targeted action scene from comedy movie B 340 basedon the per-scene classification metadata 170 associated with the variousscenes from comedy movie B. By contrast, if the user preferences 150were to indicate that the user was a comedy fan, then the video assetengine 160 would select a comedy scene from comedy movie B. As shown,the video asset engine 160 replaces the playback of the targeted actionscene from action movie E 320 with playback of the targeted action scenefrom comedy movie B 340 within the upper portion of the display 310.

Although the video asset engine 160 continues to display the movieselection menu in the lower portion of the display 310, the action fandoes not select another movie during the playback of the targeted actionscene from comedy movie B 340. Consequently, the video asset engine 160determines that the action fan has a continued interest in comedy movieB 355. In response to the continued interest in comedy movie B 355, inthe third time-snapshot, the video asset engine 160 commences a fullscreen playback of comedy movie B overlaid with playback controls 370.In some embodiments, in response to detecting continued interest, thevideo asset engine 160 commences full screen playback from a firstmeaningful scene 365 included in comedy movie B. Notably, instead ofpassively waiting for the action fan to explicitly request playback ofcomedy movie B, the video asset engine 160 preemptively selects thefirst meaningful scene 365 and begins playback in the display 310 withinthe full GUI window.

The video asset engine 160 may select the first meaningful scene 365 inany technically feasible fashion. For example, in some embodiments, theuser preferences 150 could indicate that the action fan prefers to skipopening credits and, consequently, the video asset engine 160 wouldselect the first meaningful scene 365 as the scene immediately followingthe opening credits. In other embodiments, the user preferences 150could indicate that the action fan has already viewed a portion ofcomedy movie B 355 and, therefore, the video asset engine 160 wouldselect the first meaningful scene 365 as the first scene that the actionfan has not already viewed.

Initially, the video asset engine 160 enables the action fan to overrideand/or tune the playback of comedy movie B via playback controls 370.The playback controls 370 may include any number of control mechanisms,including selections such as “start from beginning,” “pause,” “return tomovie selection menu,” “stop playback,” “go to next scene,” and soforth.

In the fourth time-snapshot, comedy movie B continues to play withoutinterruption from the action fan via the playback controls 370. Tooptimize the viewing experience, the video asset engine 160 removes theplayback controls 370 and continues a full screen playback of comedymovie B 380 within the display 310. In general, the video asset engine160 may determine whether to remove the playback controls 370 based onany number of criteria that may indicate continued user interest. Forexample, in some embodiments, if the video asset engine 160 detects nouser interactions for a pre-determined amount of time, then the videoasset engine 160 removes the playback controls 370.

In alternate embodiments, the video asset engine 160 may obtain and/orgenerate the scenes from the video assets 210 in any technicallyfeasible fashion. Further, any number of scenes may be spliced togetherto create a composite scene that the video asset engine 160 maymanipulate in lieu of a single scene. For example, in some embodiments,the video asset engine 160 may be configured to select three separate,discontinuous, scenes from the video asset 210. The video asset engine160 may select each of the scenes in any technically feasible fashion.For example, the video asset engine 160 may select one scene based onone of the user preferences 150 and select another scene based onanother of the user preferences 150 to create a personalized video. Inother embodiments, the video asset engine 160 may be configured toselect a pre-composed personalized video of multiple scenes based on theuser preferences 150.

In yet other embodiments, the video asset engine 160 may display apersonalized video in any portion of the display 130 at any point in theviewing experience. Further, the personalized video may include scenesfrom any number of the video assets 210 in any combination and based onany characteristic(s). For example, if the user preferences 150 indicatethat the comedy fan prefers a particular actor, then the video assetengine 160 may create a personalized video that includes scenes from anynumber of the video assets 210 that feature the actor. The video assetengine 160 may then present the personalized video during the videoasset selection process, as depicted in the first time-snapshot and thesecond time-snapshot of FIG. 3, or as the main viewing experience, asdepicted in the third time-snapshot and the fourth time-snapshot of FIG.3.

FIG. 4 is a flow diagram of method steps for selecting and playing backuser-relevant scenes via a graphical user interface, according tovarious embodiments of the present invention. Although the method stepsare described with reference to the systems of FIGS. 1-3, personsskilled in the art will understand that any system configured toimplement the method steps, in any order, falls within the scope of thepresent invention.

As shown, a method 400 begins at step 401, where the video asset engine160 detects the user preferences 150. At step 403, the video assetengine 160 displays still-images associated with the video assets 210.At step 405, the video asset engine 160 detects that the user hasselected the video asset 210. At step 407, the video asset engine 160determines whether the user has lost interest in the video asset 210.If, at step 407, the video asset engine 160 determines that the user haslost interest in the video asset 210, then the method 400 returns tostep 405 where the video asset engine 160 detects that the user hasselected a different video asset 210. The video asset engine 160 maydetect that the user has lost interest in the video asset 210 in anytechnically feasible fashion, such as moving away from the still-image,selecting another still-image, etc. If, however, at step 407, the videoasset engine 160 determines that the user has demonstrated continuedinterest in the video asset 210, then the method 400 proceeds to step409.

Note that the video asset engine 160 may detect that the user has bothselected and has had continued interest in the video asset 210 in anytechnically feasible fashion, such as detecting that the user ishovering over the still-image or the user has clicked on thestill-image. In alternate embodiments, however, the video asset engine160 may, based on its own logic and operation, determine to proceed tosteps 409 and 411. For example, the video asset engine 160 could selectthe video asset 210 and determine a targeted scene included within thevideo asset 210 (step 409) without any sort of trigger event and withoutreceiving any specific input from the user. In such embodiments, thevideo asset engine 160 may, for example, both select the video asset 210as well as the targeted scene included within the video asset 210 basedon the personalized user preferences 150.

At step 409, the video asset engine 160 determines a targeted sceneincluded in the video asset 210 based on the user preferences 150 andthe per-scene classification metadata 170. At step 411, the video assetengine 160 displays the video (and provides the audio) of the targetedscene. Next, at step 413, the video asset engine 160 determines whetherthe user has lost interest in the video asset 210. If, at step 413, thevideo asset engine 160 determines that the user has lost interest in thevideo asset 210, then the method 400 returns to step 405 where the videoasset engine 160 detects that the user has selected a different videoasset 210. In alternate embodiments, the video asset engine 160 mayselect a different video asset 210 without any sort of trigger event andwithout receiving any specific input from the user. If, however, at step413, the video asset engine 160 determines that the user hasdemonstrated continued interest in the video asset 210, then the method400 proceeds to step 415.

At step 415, the video asset engine 160 determines a “starting” sceneincluded in the video asset 210. The video asset engine 160 may selectthe starting scene in any technically feasible fashion based on any typeof information, such as default settings and/or the user preferences150. For example, in some embodiments, the video asset engine 160 may,by default, select the scene immediately following the opening creditsas the starting scene. At step 417, the video asset engine 160 beginsplayback of the video asset 210 from the starting scene within the fullGUI window. Although the video asset engine 160 no longer displaysstill-images associated with the video assets 210, the video assetengine 160 displays the playback controls 370 overlaid within the GUIwindow. The playback controls 370 enable the user to override and/ortune the automatic playback of the video asset 210.

At step 419, the video asset engine 170 gradually decreases thevisibility of the playback controls 270 while continuing to playback thevideo asset 210, thereby increasing the visibility of the video asset210. The video asset engine 170 may decrease the visibility of theplayback controls 270 in any technically feasible fashion, such asincrementally increasing the transparency of the playback controls 270.

At step 421, the video asset engine 160 determines whether the user haslost interest in the video asset 210. If, at step 421, the video assetengine 160 determines that the user has lost interest in the video asset210, then the method 400 returns to step 403 where the video assetengine 160 displays still-images associated with the video assets 210.The video asset engine 160 continues to cycle through steps 403-421,tailoring video marketing to reflect user interest expressed via userinteractions and the user preferences 150, until the video asset engine160 determines that the user has demonstrated continued interest in adifferent video asset 210. If, however, at step 421, the video assetengine 160 determines that the user has demonstrated continued interestin the video asset 210, then the method 400 proceeds to step 423. Atstep 423, the video asset engine 160 removes the playback controls 370and continues playback of the video asset 210.

Retaining User Interest

FIG. 5 is a conceptual diagram illustrating how the video asset engine160 displays, over time, a tailored trailer to a user, according tovarious embodiments of the present invention. The left side of FIG. 5depicts an action fan user experience 510, and the right side of FIG. 5depicts a comedy fan user experience 520. As shown, each of the actionfan user experience 510 and the comedy fan user experience 520 includesa series of four snapshots, depicting each of the viewing experiences astime passes.

Both the action fan and the comedy fan are originally viewing a movie Ain a full GUI window—labeled as display 512 and display 522respectively. In the first time-snapshot, the video asset engine 160starts displaying the credits for movie A. In the second time-snapshot,the video asset engine 160 selects and displays a targeted scene frommovie B in a small portion of the window and continues to display thecredits for movie A in the remaining portion of the window. Inoperation, the video asset engine 160 selects and displays the targetedscene based on correlating the user preferences 150 and user actionswith the per-scene classification metadata 170. Notably, the video assetengine 160 displays a targeted action scene from movie B to the actionfan but a different scene—a targeted comedy scene—from movie B to thecomedy fan.

In the third time-snapshot, the video asset engine 160 displays thetargeted scene from movie B in a larger portion of the window and theremaining portion of the window continues to display the credits formovie A. In general, the video asset engine 160 gradually replaces thecredits for movie A with the targeted scene as time progresses. In thefourth time-snapshot, the video asset engine 160 has finished displayingthe credits for movie A and is displaying the targeted scene from movieB in the full GUI window.

Although not shown in FIG. 5, the video asset engine 160 also mayprogressively reduce the volume of the credits for movie A andcorrespondingly increases the volume of the targeted scene from movie Bfrom the first time-snapshot to the fourth time-snapshot. As a generalmatter, the video asset engine 160 is configured to show different videoassets 210, such as movie A and movie B, within a GUI display.

FIG. 6 is a flow diagram of method steps for displaying a tailoredtrailer to a user, according to various embodiments of the presentinvention. Although the method steps are described with reference to thesystems of FIGS. 1-3 and 5, persons skilled in the art will understandthat any system configured to implement the method steps, in any order,falls within the scope of the present invention.

As shown, a method 600 begins at step 605, where the video asset engine160 displays the video asset 210 being viewed in a GUI window at anoriginal volume. The user may select the properties of the GUI window,such as size, and orientation, as well as the magnitude of the originalvolume in any technically feasible fashion. At step 607, the video assetengine 160 detects that the scene currently being viewed includesclosing credits.

At step 609, the video asset engine 160 selects a targeted sceneincluded in a second video based on the user preferences 150 and theper-scene classification metadata 170. For example, if the userpreferences 150 indicate that the user enjoys romance films, then thevideo asset engine 160 could select as the second video asset a romanticmovie or a movie that includes romantic scenes. The video asset engine160 could further select a targeted scene included in that video assetthat is characterized as a “romance” scene. Advantageously, the sceneselected by the video asset engine 160 is user-specific and is intendedto increase the likelihood of retaining or increasing user interest inthe second video asset.

At step 611, the video asset engine 160 gradually reduces the portion ofthe GUI window that the video asset engine 160 uses to display thecredits of the video asset 210. Substantially in parallel, the videoasset engine 160 begins playback of the targeted scene included in thesecond video asset 210 in the remaining portion of the GUI window. Aspart of step 611, the video asset engine 160 may employ a variety oftechniques to spatially and/or temporally “smooth” the transitionbetween the two video assets 210, thereby providing a high-quality userexperience. At step 613, the video asset engine 160 gradually reducesthe volume of the audio stream associated with the credits of the videoasset 210, while simultaneously increasing the volume of the audiostream for the targeted scene included in the second video asset 201.

At step 615, if the video asset engine 160 determines that the creditsof the video asset 210 have not completed, then the method 600 returnsto step 611, where the video asset engine 160 continues to graduallyreplace the video asset 210 with the targeted scene included in thesecond video asset 210. If at step 615, the video asset engine 160determines that the credits of the video asset 210 have completed, thenthe method 600 proceeds to step 617, where the video asset engine 160displays the remainder of the targeted scene included in the secondvideo asset 210 within the full GUI window at an increased volume, suchas the original volume. In this fashion, the video asset engine 160gradually transitions from the end of the video asset 210 to a targetedscene included in another video asset 210 in order to maintain userinterest by continuously displaying targeted content to the user.

In alternate embodiments, similar to the method 400 described above inFIG. 4, the video asset engine 160 may be configured to select thesecond video asset 210 based on some sort of trigger event or specificinput from the user. Once the second video asset 210 is so identified,the video asset engine 160 determines an appropriate target scene todisplay to the user based on the user preferences 150 and the per-sceneclassification metadata 170, as previously described herein. Forexample, as credits for the selected video asset 210 are playing, thevideo asset engine 160 may display a series of still-images. Based onuser selection of one of the still-images (e.g., via a mouse click or ahovering cursor), the video asset engine 160 selects the targeted scenefrom within the video asset 210 associated with the still-image based onthe user preferences 150 and the per-scene classification metadata 170,as previously described herein.

In general, the video asset engine 160 may leverage any functionalityincluded in the video asset distribution system 100 to further optimizethe viewing experience. For example, if a consumer device implementsmultiple logical decoders, then the video asset engine 160 may leveragethe multiple logical decoders to generate a cohesive viewing experiencefor the user. For example, referring back to FIG. 3, the video assetengine 160 may configure one logical decoder to display the targetedaction scene from the action movie E 320 in the upper portion of thedisplay 310 and configure another logical decoder to display thestill-images associated with the video assets 210 in the lower portionof the display 310. In another example, referring back to FIG. 5, thevideo asset engine 160 may implement a dual-decoder technique to“smooth” the spatial and/or temporal transition between the two videoassets 210 (movie A and movie B), thereby providing a high-quality userexperience.

Leveraging Multiple Decoders to Optimize Viewing Experience

FIG. 7A is a conceptual diagram illustrating how the video asset engine160 controls multiple logical decoders, according to various embodimentsof the present invention. As shown, the video asset engine 160 issuesany number of streams 712 (typically including both video and audio) toa platform 720. The platform 720 is included in the consumer device,such as the laptop 110, and includes at least one primary logicaldecoder 722 and any number of secondary logical decoders 724.

The platform 720 may be implemented in any technically feasible fashionand may be included in any consumer device. The primary logical decoders722 are capable of decoding video assets 210 in a manner that is optimalfor the platform 720. For example, if the platform 720 implementsultra-high definition (UHD), then the primary logical decoders 722 areeach capable of decoding 8.29 million pixels at 60 hertz. By contrast,if the platform 720 implements high definition (HD), then the primarylogical decoders 722 are each capable of decoding 2.07 million pixels at30 hertz. The secondary logical decoders 724 are not capable of decodingvideo assets 210 in a manner that is optimal for the platform 720 and,therefore, may be unsuitable for full screen and/or extended viewing ofthe video assets 210. For example, if the platform 720 implementsultra-high definition, then the secondary logical decoders 724 may belimited to decoding 2.07 million pixels at 30 hertz. Additionally, thesecondary logical decoders 724 may not support digital rights management(DRM). The primary logical decoders 722 and the secondary logicaldecoders 724 may be implemented in any technically feasible fashion. Forexample, in some embodiments, the primary logical decoders 722 and thesecondary logical decoders 724 may be implemented as one physicaldecoder with shared hardware, etc.

In operation, the video asset engine 160 configures the platform 720 tooptimally manage the primary logical decoders 722 and the secondarylogical decoders 724. The video asset engine 160 may configure theplatform 720 in any technically feasible fashion. For example, the videoasset engine 160 could determine relative priorities of the streams 712and set one or more characteristics associated with the streams 712based on the priorities. Such characteristics would indirectly cause theplatform 720 to optimally route the streams 712 to the different primarylogical decoders 722 and the secondary logical decoders 724 for displaypurposes. Examples of such characteristics include display resolution,display area, decoder type (e.g., primary or secondary), etc. In someembodiments, to more effectively transition the video asset 210 frombeing displayed via the secondary logical decoder 724 to being displayedvia the primary logical decoder 722, the video asset engine 160 maytransmit a transition image, such as a spinner (e.g., a sequence ofstill-images that indicates progress such as a wheel or bar), a blankscreen, or the like.

As persons skilled in the art will recognize, in some embodiments, theplatform 720 manages a “global performance envelope”—a restriction onthe maximum throughput of all the primary logical decoders 722 and thesecondary logical decoders 724 included in the platform 720. Typically,the global performance envelope is measured in macroblocks per second(MBPS) and allows for the fractional representation of performance. Forexample, in a dual decoder platform 720, if the primary logical decoder722 were to have a performance capability of 1080p at 30 hertz and thesecondary logical decoder 724 were to have a performance capability of480p at 30 hertz, then the global performance envelope would be 285,300MBPS.

Typically, as part of managing the global performance envelope, theplatform 720 buffers the streams 712 in a holistic manner that reflectsthe characteristics of the streams 712. To enable the platform 720 tooptimally manage the global performance envelope for the streams 712 aspart of decoder switching operations, the video asset engine 160 may beconfigured to issue an expected stream change notification 714 to theplatform 720. The stream change notification 714 enables the platform720 to modify operations, such as buffering, in preparation for upcomingchanges in the streams 712.

For example, referring back to FIG. 5, as time passes, the video assetengine 160 could decrease the priority of the stream 712(1) associatedwith Movie A and increase the priority of the stream 712(2) associatedwith movie B. Based on these priorities, the video asset engine 160could set the resolution and display area associated with each of thestreams 712 such that the platform 720 re-routes the stream 712(2) fromthe secondary logical decoder 724 to the primary logical decoder 722. Toensure that the platform 720 optimally buffers the streams 712 as partof the re-routing, the video asset engine 160 could issue the expectedstream change notification 714 before changing the display resolutionsand display areas associated with the streams 712. More specifically,the video asset engine 160 could configure the platform 720 tocompensate for a network buffer depth 755 (measured in time) thatreflects the global performance envelope managed by the platform 720.

FIG. 7B is a conceptual diagram illustrating how the video asset engine160 compensates for the network buffer depth 755 according to variousembodiments of the present invention. In operation, the video assetengine 160 sets the characteristics of the streams 712 and issues theexpected stream change notification 714 that configures the platform 720to perform the operations illustrated in FIG. 7B.

Initially, the video asset engine 160 sets the display resolution of thestream 712(1) associated with the movie A to an optimal resolution,causing the platform 720 to buffer the stream 712(1) at the optimalresolution and then begins to playback the movie A at the optimalresolution.

After some time passes, the video asset engine 160 issues the expectedstream change notification 714, reduces the display resolution of thestream 712(1), and sets the display resolution of the stream 712(2)associated with the movie B to an intermediate resolution. Theintermediate resolution lies between the optimal resolution and thereduced resolution at a value commiserate with the global performanceenvelope.

In response to the expected stream change notification 712, the platform720 begins buffering movie A at the reduced resolution instead of theoptimal resolution. The platform 720 then begins buffering the movie Bat the intermediate resolution. After the network buffer depth 755 haspassed, the platform 720 begins playback of movie A at the reducedresolution and playback of movie B at the intermediate resolution.

FIG. 8 is a flow diagram of method steps for displaying video assets viamultiple decoders, according to various embodiments of the presentinvention. Although the method steps are described with reference to thesystems of FIGS. 1-3, 5, and 7, persons skilled in the art willunderstand that any system configured to implement the method steps, inany order, falls within the scope of the present invention.

As shown, a method 800 begins at step 803, where the video asset engine160 determines a current priority for a current stream 712 that isassociated with a current video asset 210. At step 805, the video assetengine 160 sets a display resolution associated with the current stream712 based on the current priority and commiserate with the capabilitiesof the primary decoder 722 included in the platform 720. The video assetengine 160 may determine the current priority and the display resolutionin any technically feasible fashion based on any relevant information.For example, the video asset engine 160 may select the displayresolution from a set of available display resolutions associated withthe video asset 210 and based on the global performance envelope managedby the platform 720.

At step 807, the video asset engine 160 configures the platform 720 tobuffer and display the current stream 712 via the primary decoder 722.The video asset engine 160 may configure the platform 720 in anytechnically feasible fashion using direct and/or indirect techniques inany combination. For example, in some embodiments, the video assetengine 160 may set the values of one or more characteristics associatedwith the current stream 712. In other embodiments, the video assetengine 160 may determine that one or more characteristics associatedwith the current stream 712 indirectly cause the platform 720 to bufferand display the current stream 712 in the desired manner. The videoasset engine 160 then transmits the current stream 712 to the platform720 for display purposes.

At step 809, the video asset engine 160 determines a next priority for anext stream 712. At step 811, the video asset engine 160 performs acomparison between the current priority and the next priority. Based onthe results of the comparison, the video asset engine 160 reduces thedisplay resolution of the current stream 712 and sets the displayresolution associated with the next stream 712 to an intermediate value.The video asset engine 160 may determine the next priority and thedisplay resolutions in any technically feasible fashion. For example, ifthe current stream 712 was associated with a feature film and the nextstream 712 was associated with a teaser video, then the video assetengine 160 could set the next priority to a relatively low valuecompared to the current priority. Further, based on these relativepriorities, the video asset engine 160 could reduce the displayresolution associated with the current stream and set the displayresolution associated with the next stream to a value lower than thereduced display resolution. In some embodiments, the video asset engine160 may set the display resolution associated with the current streamand the display resolution associated with the next stream based on theglobal performance envelope managed by the platform 720.

At step 813, the video asset engine 160 configures the platform 720 tobuffer and display the next stream 712 via the secondary decoder 724.The video asset engine 160 may configure the platform 720 in anytechnically feasible fashion using either direct or indirect techniquesNotably, after configuring the platform 720 to buffer and display thenext stream 712, the video asset engine 160 transmits both the currentstream 712 and the next stream 712 to the platform 720 for displaypurposes.

At step 815, the video asset engine 160 determines whether the user hasdemonstrated interest in the next stream 712. If, at step 815, the videoasset engine 160 determines that the user has relatively little interestin the next stream 712, then the method 800 returns to step 809 wherethe video asset engine 160 selects a different next stream 712. If,however, at step 815, the video asset engine 160 determines that theuser has demonstrated continued interest in the next stream 712, thenthe method 800 proceeds to step 817. Note that the video asset engine160 may detect that the user has continued interest in the next stream712 in any technically feasible fashion.

At step 817, the video asset engine 160 transmits the expected streamchange notification 714 to the platform 720. More specifically, thevideo asset engine 160 notifies the platform 720 to prepare for a switchfrom displaying the next stream 712 via the secondary decoder 724 todisplaying the next stream 712 via the primary decoder 722. The videoasset engine 160 orchestrates such a switch to optimize the viewingexperience for the user as per the demonstrated interest of the user.

At step 819, the video asset engine 160 increases the display resolutionassociated with the next stream 712. In response, the platform 720begins to buffer the next stream 712 at the increased resolution. Atstep 821, the video asset engine 160 ceases to transmit the currentstream 712. At step 823, the video asset engine 160 configures theplatform 720 to display the next stream 712 via the primary decoder 722instead of the secondary decoder 724. In this manner, based on detecteduser interest, the video asset engine 160 leverages the primary decoder722 and the secondary decoder 724 included in the platform 720 tooptimize the viewing experience.

In sum, among other things, embodiments of the present invention aredirected towards enhancing user interest in video merchandising. In someembodiments of the present invention, a video asset engine leverages avideo dissection capability that decomposes a video into scenes andgenerates scene-specific classification metadata to select user-relevantscenes from within video assets. In addition, in some embodiments of thepresent invention, the video asset engine dynamically adjusts playbackbetween two video streams to strategically transition user interest. Inparticular, as one video asset is ending, the video asset engine selectsa scene included in another video asset to reflect user preferences andincrementally replace the ending video asset with the selected scene.

In various embodiments, the video asset engine configures any number ofdecoders to simultaneously display multiple scenes, where each scene isincluded in one of the video assets. In yet other embodiments, the videoasset engine configures multiple decoders to work together to providesmooth transitions as the video asset engine displays different videoassets.

Advantageously, by tailoring scene selection and integrating playback ofselected scenes into an overall viewing experience, the video assetengine increases the probability of acquiring and maintaining userinterest in video assets. More specifically, by selecting personalizedscenes and presenting the selected scenes in a contextually-relevantmanner, the video asset engine is able to more effectively convince theuser that he or she would enjoy viewing the selected video asset.Further, by predicting a loss of interest in a current video asset(e.g., playback of ending credits) and seamlessly redirecting viewerinterest to additional video assets via multiple decoders, the videoasset engine generates an immersive and targeted viewing experience.

The descriptions of the various embodiments have been presented forpurposes of illustration, but are not intended to be exhaustive orlimited to the embodiments disclosed. Many modifications and variationswill be apparent to those of ordinary skill in the art without departingfrom the scope and spirit of the described embodiments.

Aspects of the present embodiments may be embodied as a system, methodor computer program product. Accordingly, aspects of the presentdisclosure may take the form of an entirely hardware embodiment, anentirely software embodiment (including firmware, resident software,micro-code, etc.) or an embodiment combining software and hardwareaspects that may all generally be referred to herein as a “circuit,”“module” or “system.” Furthermore, aspects of the present disclosure maytake the form of a computer program product embodied in one or morecomputer readable medium(s) having computer readable program codeembodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

Aspects of the present disclosure are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, enable the implementation of the functions/acts specified inthe flowchart and/or block diagram block or blocks. Such processors maybe, without limitation, general purpose processors, special-purposeprocessors, application-specific processors, or field-programmableprocessors or gate arrays.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

While the preceding is directed to embodiments of the presentdisclosure, other and further embodiments of the disclosure may bedevised without departing from the basic scope thereof, and the scopethereof is determined by the claims that follow.

What is claimed is:
 1. A computer-implemented method, comprising:selecting a first scene included in a first video asset based on one ormore preferences and metadata associated with a plurality of scenes,wherein the first video asset is included in a plurality of videoassets, and each scene included in the plurality of scenes is includedin one of the video assets included in the plurality of video assets;and displaying the first scene within a first portion of a display area;predicting a loss of interest in the first video asset; and in response,causing the size of the first portion of the display area to decrease,selecting a second scene included in a second video asset based on theone or more preferences and the metadata, and displaying the secondscene in a second portion of the display area.
 2. The method of claim 1,further comprising causing, over time, the size of the first portion ofthe display area to decrease and the size of the second portion of thedisplay area to increase.
 3. The method of claim 1, wherein predictingthe loss of interest comprises preparing to display a third sceneincluded in the first video asset within the first portion of thedisplay area, and determining that the third scene includes one or moreending credits.
 4. A non-transitory computer-readable medium includinginstructions that, when executed by a processor, cause the processor toperform the steps of: selecting a first scene included in a first videoasset based on one or more preferences and metadata associated with aplurality of scenes, wherein the first video asset is included in aplurality of video assets, and each scene included in the plurality ofscenes is included in one of the video assets included in the pluralityof video assets; and displaying the first scene within a first portionof a display area; predicting a loss of interest in the first videoasset; and in response, causing the size of the first portion of thedisplay area to decrease, selecting a second scene included in a secondvideo asset based on the one or more preferences and the metadata, anddisplaying the second scene in a second portion of the display area. 5.The non-transitory computer-readable medium of claim 4, furthercomprising causing, over time, the size of the first portion of thedisplay area to decrease and the size of the second portion of thedisplay area to increase.
 6. The non-transitory computer-readable mediumof claim 4, wherein predicting the loss of interest comprises preparingto display a third scene included in the first video asset within thefirst portion of the display area, and determining that the third sceneincludes one or more ending credits.
 7. A system, comprising: a memorystoring instructions; and a processor that is coupled to the memory and,when executing the instructions, is configured to: select a first sceneincluded in a first video asset based on one or more preferences andmetadata associated with a plurality of scenes, wherein the first videoasset is included in a plurality of video assets, and each sceneincluded in the plurality of scenes is included in one of the videoassets included in the plurality of video assets; and display the firstscene within a first portion of a display area; predict a loss ofinterest in the first video asset; and in response, cause the size ofthe first portion of the display area to decrease, select a second sceneincluded in a second video asset based on the one or more preferencesand the metadata, and display the second scene in a second portion ofthe display area.